Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OCPBUGS-48044: [Nutanix] Install multi-NICs cluster failed with failureDomains #9376

Merged
merged 2 commits into from
Feb 5, 2025
Merged

OCPBUGS-48044: [Nutanix] Install multi-NICs cluster failed with failureDomains #9376

merged 2 commits into from
Feb 5, 2025

Conversation

yanhua121
Copy link
Contributor

OCPBUGS-48044:
[Nutanix] Install multi-NICs cluster failed with failureDomains

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 17, 2025
@openshift-ci-robot
Copy link
Contributor

@yanhua121: This pull request references Jira Issue OCPBUGS-48044, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

OCPBUGS-48044:
[Nutanix] Install multi-NICs cluster failed with failureDomains

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@yanhua121
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@yanhua121: This pull request references Jira Issue OCPBUGS-48044, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from barbacbd and jhixson74 January 17, 2025 15:55
@yanhua121
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 17, 2025
@openshift-ci-robot
Copy link
Contributor

@yanhua121: This pull request references Jira Issue OCPBUGS-48044, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from gpei January 17, 2025 15:57
@yanhua121
Copy link
Contributor Author

/retest-required

@yanhua121
Copy link
Contributor Author

/retest

@yanhua121
Copy link
Contributor Author

/retest-required

@jhixson74
Copy link
Member

Can you break the commits up here? A description of the fix would be nice too.

@yanhua121
Copy link
Contributor Author

/retest-required

@yanhua121 yanhua121 force-pushed the OCPBUGS-48044 branch 2 times, most recently from 23f18a6 to 51e404f Compare January 28, 2025 18:39
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 28, 2025
@yanhua121
Copy link
Contributor Author

/retest-required

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 30, 2025
@yanhua121
Copy link
Contributor Author

/retest-required

@yanhua121
Copy link
Contributor Author

/retest

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 1, 2025

@yanhua121: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-azurestack 2ed5a34 link false /test e2e-azurestack
ci/prow/e2e-vsphere-host-groups-ovn-custom-no-upgrade 2ed5a34 link false /test e2e-vsphere-host-groups-ovn-custom-no-upgrade
ci/prow/okd-scos-e2e-aws-ovn 2ed5a34 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node 2ed5a34 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-azure-ovn-shared-vpc 2ed5a34 link false /test e2e-azure-ovn-shared-vpc
ci/prow/e2e-aws-ovn-edge-zones 2ed5a34 link false /test e2e-aws-ovn-edge-zones

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yanhua121
Copy link
Contributor Author

/assign @r4f4

@r4f4
Copy link
Contributor

r4f4 commented Feb 3, 2025

/unassign
/assign @jhixson74

@openshift-ci openshift-ci bot assigned jhixson74 and unassigned r4f4 Feb 3, 2025
@yanhua121
Copy link
Contributor Author

/test e2e-nutanix-ovn

@jcpowermac
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2025
@yanhua121
Copy link
Contributor Author

/assign @patrickdillon

@patrickdillon
Copy link
Contributor

/approve
/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 4, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 4, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 6fec4c8 into openshift:main Feb 5, 2025
38 of 44 checks passed
@openshift-ci-robot
Copy link
Contributor

@yanhua121: Jira Issue OCPBUGS-48044: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-48044 has been moved to the MODIFIED state.

In response to this:

OCPBUGS-48044:
[Nutanix] Install multi-NICs cluster failed with failureDomains

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.19.0-202502050358.p0.g6fec4c8.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.19.0-202502050358.p0.g6fec4c8.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.19.0-202502050358.p0.g6fec4c8.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.19.0-202502050358.p0.g6fec4c8.assembly.stream.el9.
All builds following this will include this PR.

@yanhua121
Copy link
Contributor Author

/cherrypick release-4.18

@openshift-cherrypick-robot
Copy link

@yanhua121: Failed to get PR patch from GitHub. This PR will need to be manually cherrypicked.

Error messagestatus code 406 not one of [200], body: {"message":"Sorry, the diff exceeded the maximum number of files (300). Consider using 'List pull requests files' API or locally cloning the repository instead.","errors":[{"resource":"PullRequest","field":"diff","code":"too_large"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#list-pull-requests-files","status":"406"}

In response to this:

/cherrypick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@yanhua121 yanhua121 mentioned this pull request Feb 10, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@barbacbd barbacbd

@jhixson74 jhixson74

@gpei gpei

Assignees

@jhixson74 jhixson74

@patrickdillon patrickdillon

@jcpowermac jcpowermac

Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
9 participants
@yanhua121 @openshift-ci-robot @jhixson74 @r4f4 @jcpowermac @patrickdillon @openshift-bot @openshift-cherrypick-robot @openshift-merge-robot